👷 Deploy Preview for 3dstreet-core-builds processing.

Thanks for the start

• * The current location of the geospatial long/lat should display in the geomodal if it is available
• * searching for location should work as expected
• * the design of main.js footer section should roughly match: restyle of footer buttons and title #589 (note the relocated help icon; here is figma link: https://www.figma.com/design/W9jid3A0jgssnIKBFEvG38/3DStreet-2022?node-id=6555-175608&t=tzhDzsJib77eAp8r-4)
• * Coordinate field handler to allow user to enter coordinates and change map
• * ?Location label in geopanel: shows as "SF, CA at Market and Van Ness" as static. We could instead show longitude and latitude? If no location then "Click to set location". Clicking on location text can be same action as clicking on icon
• * ?add an elevation number entry field beneath centerpoint lat/lon field?

Another question is make the coordinate field read-only or add a handler to allow user to enter coordinates and change the map? Because now an error appears when changing coordinates via input

Error while saving

"Error trying to save 3DStreet scene to cloud. Error: RangeError: Maximum call stack size exceeded"

If add 'reference-layers' to the skipChildrenNodes array in json-utils.js in the getElementData function, its children will not be saved in JSON. This fixes a stack overload bug when saving for now.
But I understand that the reason is different, of course

Ok. It looks like it all working now. I just noticed that the aspect ratio of the camera in Plan View does not adapt to the screen. I need to fix this.

Ok. It looks like it all working now.

It looks like the geopanel does not display the long/lat/elevation as it did before. I testing other stuff to see if it's all working

I just noticed that the aspect ratio of the camera in Plan View does not adapt to the screen. I need to fix this.

Yes, although I think this was already a solved problem in the a-frame inspector so there may be an easy fix to port over. 3DStreet/3dstreet-editor#185

It looks like the geopanel does not display the long/lat/elevation as it did before. I testing other stuff to see if it's all working

thanks, I forgot about this. Yesterday I spent half a day debugging the work of 3dtiles + Editor. Was focused on this.

@Algorush did testing today and the only "showstopper" issue I found was elevation is a confusing thing for user to edit directly, instead it would be helpful to provide that value on behalf of the user.

In this glitch project there is an example of vanilla js method using ElevationService to get elevation for a given lat / lon. I would suggest that we do the same thing -- when a user clicks on a place on the map, the elevation is updated based on that lat/lon.

https://glitch.com/edit/#!/bollard-buddy-qr-maker?path=script.js%3A43%3A0

    // Get the elevation at the clicked location    
    const elevator = new google.maps.ElevationService();
    elevator.getElevationForLocations({
      locations: [mapsMouseEvent.latLng],
    }, function(elevationResponse, status) {
      if (status === 'OK' && elevationResponse && elevationResponse.length > 0) {
        const elevation = elevationResponse[0].elevation;
        console.log('Elevation:', elevation);
        // Use the elevation value as needed...

@Algorush did testing today and the only "showstopper" issue I found was elevation is a confusing thing for user to edit directly, instead it would be helpful to provide that value on behalf of the user.

In this glitch project there is an example of vanilla js method using ElevationService to get elevation for a given lat / lon. I would suggest that we do the same thing -- when a user clicks on a place on the map, the elevation is updated based on that lat/lon.

Thanks! I didn't know about this feature on google maps. I'll get it to set elevation.
So, do this - set the elevation level using this request to google.maps.elevationService. But leave the elevation field so that the user can change it?

So, do this - set the elevation level using this request to google.maps.elevationService. But leave the elevation field so that the user can change it?

Yes, in other words if a user chooses a new lat / long, then overwrite any existing elevation value with the new elevation value from the ElevationService in the modal dialog. Of course, the user still may choose to cancel and their existing scene elevation is not overwritten, but I assume that if they choose a new location they will want the elevation calculated automatically, at least at first.